Method and apparatus for accessing secure data in a dispersed storage system

ABSTRACT

A method begins with a first computing device receiving a first request from a user device to access secure data. The method continues with the first computing device processing the first request to determine a level of access. When the level of access is acceptable, the method continues with the first computing device facilitating sending a set of encoded data slices to the user device. The method continues with a second computing device receiving a second request from the user device. The method continues with the second computing device processing the second request to determine the level of access. When the level of access is acceptable, the method continues with the second computing device facilitating sending a second set of encoded data slices to the user device. When the level of access is at a given level, the sets include a reconstruction threshold number of encoded data slices.

CROSS REFERENCE TO RELATED PATENTS

The present U.S. Utility patent application claims priority pursuant to35 U.S.C. §121 as a divisional of U.S. Utility application Ser. No.12/797,165, entitled “METHOD AND APPARATUS FOR ACCESSING SECURE DATA INA DISPERSED STORAGE SYSTEM”, filed Jun. 9, 2010, issuing as U.S. Pat.No. 8,689,354 on Apr. 1, 2014, which is hereby incorporated herein byreference in its entirety and made part of the present U.S. Utilitypatent application for all purposes.

U.S. Utility application Ser. No. 12/797,165 claims priority pursuant to35 U.S.C. §119(e) to U.S. Provisional Application No. 61/246,809,entitled “FINANCIAL TRANSACTIONS UTILIZING A DISTRIBUTED STORAGENETWORK”, filed Sep. 29, 2009.

STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT

Not Applicable

INCORPORATION-BY-REFERENCE OF MATERIAL SUBMITTED ON A COMPACT DISC

Not Applicable

BACKGROUND OF THE INVENTION

1. Technical Field of the Invention

This invention relates generally to computing systems and moreparticularly to data storage solutions within such computing systems.

2. Description of Related Art

Computers are known to communicate, process, and store data. Suchcomputers range from wireless smart phones to data centers that supportmillions of web searches, stock trades, or on-line purchases every day.In general, a computing system generates data and/or manipulates datafrom one form into another. For instance, an image sensor of thecomputing system generates raw picture data and, using an imagecompression program (e.g., JPEG, MPEG, etc.), the computing systemmanipulates the raw picture data into a standardized compressed image.

With continued advances in processing speed and communication speed,computers are capable of processing real time multimedia data forapplications ranging from simple voice communications to streaming highdefinition video. As such, general-purpose information appliances arereplacing purpose-built communications devices (e.g., a telephone). Forexample, smart phones can support telephony communications but they arealso capable of text messaging and accessing the internet to performfunctions including email, web browsing, remote applications access, andmedia communications (e.g., telephony voice, image transfer, musicfiles, video files, real time video streaming. etc.).

Each type of computer is constructed and operates in accordance with oneor more communication, processing, and storage standards. As a result ofstandardization and with advances in technology, more and moreinformation content is being converted into digital formats. Forexample, more digital cameras are now being sold than film cameras, thusproducing more digital pictures. As another example, web-basedprogramming is becoming an alternative to over the air televisionbroadcasts and/or cable broadcasts. As further examples, papers, books,video entertainment, home video, etc. are now being stored digitally,which increases the demand on the storage function of computers.

A typical computer storage system includes one or more memory devicesaligned with the needs of the various operational aspects of thecomputer's processing and communication functions. Generally, theimmediacy of access dictates what type of memory device is used. Forexample, random access memory (RAM) memory can be accessed in any randomorder with a constant response time, thus it is typically used for cachememory and main memory. By contrast, memory device technologies thatrequire physical movement such as magnetic disks, tapes, and opticaldiscs, have a variable response time as the physical movement can takelonger than the data transfer, thus they are typically used forsecondary memory (e.g., hard drive, backup memory, etc.).

A computer's storage system will be compliant with one or more computerstorage standards that include, but are not limited to, network filesystem (NFS), flash file system (FFS), disk file system (DFS), smallcomputer system interface (SCSI), internet small computer systeminterface (iSCSI), file transfer protocol (FTP), and web-baseddistributed authoring and versioning (WebDAV). These standards specifythe data storage format (e.g., files, data objects, data blocks,directories, etc.) and interfacing between the computer's processingfunction and its storage system, which is a primary function of thecomputer's memory controller.

Despite the standardization of the computer and its storage system,memory devices fail; especially commercial grade memory devices thatutilize technologies incorporating physical movement (e.g., a discdrive). For example, it is fairly common for a disc drive to routinelysuffer from bit level corruption and to completely fail after threeyears of use. One solution is to a higher-grade disc drive, which addssignificant cost to a computer.

Another solution is to utilize multiple levels of redundant disc drivesto replicate the data into two or more copies. One such redundant driveapproach is called redundant array of independent discs (RAID). In aRAID device, a RAID controller adds parity data to the original databefore storing it across the array. The parity data is calculated fromthe original data such that the failure of a disc will not result in theloss of the original data. For example, RAID 5 uses three discs toprotect data from the failure of a single disc. The parity data, andassociated redundancy overhead data, reduces the storage capacity ofthree independent discs by one third (e.g., n−1=capacity). RAID 6 canrecover from a loss of two discs and requires a minimum of four discswith a storage capacity of n−2.

While RAID addresses the memory device failure issue, it is not withoutits own failures issues that affect its effectiveness, efficiency andsecurity. For instance, as more discs are added to the array, theprobability of a disc failure increases, which increases the demand formaintenance. For example, when a disc fails, it needs to be manuallyreplaced before another disc fails and the data stored in the RAIDdevice is lost. To reduce the risk of data loss, data on a RAID deviceis typically copied on to one or more other RAID devices. While thisaddresses the loss of data issue, it raises a security issue sincemultiple copies of data are available, which increases the chances ofunauthorized access. Further, as the amount of data being stored grows,the overhead of RAID devices becomes a non-trivial efficiency issue.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING(S)

FIG. 1 is a schematic block diagram of an embodiment of a computingsystem in accordance with the invention;

FIG. 2 is a schematic block diagram of an embodiment of a computing corein accordance with the invention;

FIG. 3 is a schematic block diagram of an embodiment of a distributedstorage processing unit in accordance with the invention;

FIG. 4 is a schematic block diagram of an embodiment of a grid module inaccordance with the invention;

FIG. 5 is a diagram of an example embodiment of error coded data slicecreation in accordance with the invention;

FIG. 6 is a flowchart illustrating the determination of a disguisedslice name;

FIG. 7 is a flowchart illustrating the creation and storage of anauthorization request and the retrieval and processing of anauthorization request response;

FIG. 8 is a flowchart illustrating the retrieval and processing of anauthorization request and the creation and storage of an authorizationrequest response;

FIG. 9 is a flowchart illustrating the creation and storage of asettlement request;

FIG. 10 is a flowchart illustrating the retrieval and processing of asettlement request;

FIG. 11 is a flowchart illustrating the retrieval of accountinformation;

FIG. 12 is a flowchart illustrating the retrieval of information;

FIG. 13 is a flowchart illustrating secure access of dispersedly storeddata by a processing module; and

FIG. 14 is another flowchart illustrating secure access of dispersedlystored data by a processing module.

DETAILED DESCRIPTION OF THE INVENTION

FIG. 1 is a schematic block diagram of a computing system 10 thatincludes one or more of a first type of user devices 12, one or more ofa second type of user devices 14, one or more readers 15, at least onedistributed storage (DS) processing unit 16, at least one DS managingunit 18, at least one storage integrity processing unit 20, at least onetransaction unit 21, and a distributed storage network (DSN) memory 22coupled via a network 24. The network 24 may include one or morewireless and/or wire lined communication systems; one or more privateintranet systems and/or public internet systems; and/or one or morelocal area networks (LAN) and/or wide area networks (WAN).

The DSN memory 22 includes a plurality of distributed storage (DS) units36 for storing data of the system. Each of the DS units 36 includes aprocessing module and memory and may be located at a geographicallydifferent site than the other DS units (e.g., one in Chicago, one inMilwaukee, etc.). The processing module may be a single processingdevice or a plurality of processing devices. Such a processing devicemay be a microprocessor, micro-controller, digital signal processor,microcomputer, central processing unit, field programmable gate array,programmable logic device, state machine, logic circuitry, analogcircuitry, digital circuitry, and/or any device that manipulates signals(analog and/or digital) based on hard coding of the circuitry and/oroperational instructions. The processing module may have an associatedmemory and/or memory element, which may be a single memory device, aplurality of memory devices, and/or embedded circuitry of the processingmodule. Such a memory device may be a read-only memory, random accessmemory, volatile memory, non-volatile memory, static memory, dynamicmemory, flash memory, cache memory, and/or any device that storesdigital information. Note that if the processing module includes morethan one processing device, the processing devices may be centrallylocated (e.g., directly coupled together via a wired and/or wireless busstructure) or may be distributedly located (e.g., cloud computing viaindirect coupling via a local area network and/or a wide area network).Further note that when the processing module implements one or more ofits functions via a state machine, analog circuitry, digital circuitry,and/or logic circuitry, the memory and/or memory element storing thecorresponding operational instructions may be embedded within, orexternal to, the circuitry comprising the state machine, analogcircuitry, digital circuitry, and/or logic circuitry. Still further notethat, the memory element stores, and the processing module executes,hard coded and/or operational instructions corresponding to at leastsome of the steps and/or functions illustrated in FIGS. 1-12.

Each of the user devices 12-14, the reader 15, the DS processing unit16, the DS managing unit 18, the storage integrity processing unit 20,and the transaction unit 21 may be a portable computing device (e.g., apoint of sale terminal, a social networking device, a gaming device, acell phone, a smart phone, a personal digital assistant, a digital musicplayer, a digital video player, a laptop computer, a handheld computer,a video game controller, and/or any other portable device that includesa computing core) and/or a fixed computing device (e.g., a point of saleterminal, a personal computer, a computer server, a cable set-top box, asatellite receiver, a television set, a printer, a fax machine, homeentertainment equipment, a video game console, and/or any type of homeor office computing equipment). Such a portable or fixed computingdevice includes a computing core 26 and one or more interfaces 30, 32,and/or 33. An embodiment of the computing core 26 will be described withreference to FIG. 2.

With respect to the interfaces, each of the interfaces 30, 32, and 33includes software and/or hardware to support one or more communicationlinks via the network 24 and/or directly. For example, interfaces 30support a communication link (wired, wireless, direct, via a LAN, viathe network 24, etc.) between the first type of user device 14 and theDS processing unit 16. As another example, DSN interface 32 supports aplurality of communication links via the network 24 between the DSNmemory 22 and the DS processing unit 16, the first type of user device12, the storage integrity processing unit 20, and/or the transactionunit 21. As yet another example, interface 33 supports a communicationlink between the DS managing unit 18 and any one of the other devicesand/or units 12, 14, 16, 20, and/or 22 via the network 24.

In general and with respect to data storage, the system 10 supportsthree primary functions: distributed network data storage management,distributed data storage and retrieval, and data storage integrityverification. In accordance with these three primary functions, data canbe distributedly stored in a plurality of physically different locationsand subsequently retrieved in a reliable and secure manner regardless offailures of individual storage devices, failures of network equipment,the duration of storage, the amount of data being stored, attempts athacking the data, etc.

The DS managing unit 18 performs distributed network data storagemanagement functions, which include establishing distributed datastorage parameters, performing network operations, performing networkadministration, and/or performing network maintenance. The DS managingunit 18 establishes the distributed data storage parameters (e.g.,allocation of virtual DSN memory space, distributed storage parameters,security parameters, billing information, user profile information,etc.) for one or more of the user devices 12-14 (e.g., established forindividual devices, established for a user group of devices, establishedfor public access by the user devices, etc.). For example, the DSmanaging unit 18 coordinates the creation of a vault (e.g., a virtualmemory block) within the DSN memory 22 for a user device (for a group ofdevices, or for public access). The DS managing unit 18 also determinesthe distributed data storage parameters for the vault. In particular,the DS managing unit 18 determines a number of slices (e.g., the numberthat a data segment of a data file and/or data block is partitioned intofor distributed storage) and a read threshold value (e.g., the minimumnumber of slices required to reconstruct the data segment).

As another example, the DS managing module 18 creates and stores,locally or within the DSN memory 22, user profile information. The userprofile information includes one or more of authentication information,permissions, and/or the security parameters. The security parameters mayinclude one or more of encryption/decryption scheme, one or moreencryption keys, key generation scheme, and data encoding/decodingscheme.

As yet another example, the DS managing unit 18 creates billinginformation for a particular user, user group, vault access, publicvault access, etc. For instance, the DS managing unit 18 tracks thenumber of times user accesses a private vault and/or public vaults,which can be used to generate a per-access bill. In another instance,the DS managing unit 18 tracks the amount of data stored and/orretrieved by a user device and/or a user group, which can be used togenerate a per-data-amount bill.

The DS managing unit 18 also performs network operations, networkadministration, and/or network maintenance. As at least part ofperforming the network operations and/or administration, the DS managingunit 18 monitors performance of the devices and/or units of the system10 for potential failures, determines the devices and/or unit'sactivation status, determines the devices' and/or units' loading, andany other system level operation that affects the performance level ofthe system 10. For example, the DS managing unit 18 receives andaggregates network management alarms, alerts, errors, statusinformation, performance information, and messages from the devices12-14 and/or the units 16, 20, 22. For example, the DS managing unit 18receives a simple network management protocol (SNMP) message regardingthe status of the DS processing unit 16.

The DS managing unit 18 performs the network maintenance by identifyingequipment within the system 10 that needs replacing, upgrading,repairing, and/or expanding. For example, the DS managing unit 18determines that the DSN memory 22 needs more DS units 36 or that one ormore of the DS units 36 needs updating.

The second primary function (i.e., distributed data storage andretrieval) begins and ends with a user device 12-14. The user device12-14 may have the reader 15 operably coupled to the computing core 26of the user device 12-14. The reader 15 may be internal (e.g.,integrated) to the user device 12 or external to the user device 14. Thereader 15 functions as one or more of a credit card reader, a smart cardreader, a radio frequency identifier (RFID) tag reader, and a near fieldcommunications (NFC) reader. The user device 12-14 generates a data file38 and/or data block 40 based on card data 17 from the reader 15. Thecard data 17 includes credit card account information including anaccount number, card holder name, and/or issuer identifier.

In another instance, if a second type of user device 14 has a data file38 and/or data block 40 to store in the DSN memory 22, it send the datafile 38 and/or data block 40 to the DS processing unit 16 via itsinterface 30. As will be described in greater detail with reference toFIG. 2, the interface 30 functions to mimic a conventional operatingsystem (OS) file system interface (e.g., network file system (NFS),flash file system (FFS), disk file system (DFS), file transfer protocol(FTP), web-based distributed authoring and versioning (WebDAV), etc.)and/or a block memory interface (e.g., small computer system interface(SCSI), internet small computer system interface (iSCSI), etc.). Inaddition, the interface 30 may attach a user identification code (ID) tothe data file 38 and/or data block 40.

The DS processing unit 16 receives the data file 38 and/or data block 40via its interface 30 and performs a distributed storage (DS) process 34thereon (e.g., an error coding dispersal storage function). The DSprocessing 34 begins by partitioning the data file 38 and/or data block40 into one or more data segments, which is represented as Y datasegments. For example, the DS processing 34 may partition the data file38 and/or data block 40 into a fixed byte size segment (e.g., 2¹ to2^(n) bytes, where n=>2) or a variable byte size (e.g., change byte sizefrom segment to segment, or from groups of segments to groups ofsegments, etc.).

For each of the Y data segments, the DS processing 34 error encodes(e.g., forward error correction (FEC), information dispersal algorithm,or error correction coding) and slices (or slices then error encodes)the data segment into a plurality of error coded (EC) data slices 42-48,which is represented as X slices per data segment. The number of slices(X) per segment, which corresponds to a number of pillars n, is set inaccordance with the distributed data storage parameters and the errorcoding scheme. For example, if a Reed-Solomon (or other FEC scheme) isused in an n/k system, then a data segment is divided into n slices,where k number of slices is needed to reconstruct the original data(i.e., k is the threshold). As a few specific examples, the n/k factormay be 5/3; 6/4; 8/6; 8/5; 16/10.

For each slice 42-48, the DS processing unit 16 creates a unique slicename and appends it to the corresponding slice 42-48. The slice nameincludes universal DSN memory addressing routing information (e.g.,virtual memory addresses in the DSN memory 22) and user-specificinformation (e.g., user ID, file name, data block identifier, etc.).

The DS processing unit 16 transmits the plurality of EC slices 42-48 toa plurality of DS units 36 of the DSN memory 22 via the DSN interface 32and the network 24. The DSN interface 32 formats each of the slices fortransmission via the network 24. For example, the DSN interface 32 mayutilize an internet protocol (e.g., TCP/IP, etc.) to packetize theslices 42-48 for transmission via the network 24.

The number of DS units 36 receiving the slices 42-48 is dependent on thedistributed data storage parameters established by the DS managing unit18. For example, the DS managing unit 18 may indicate that each slice isto be stored in a different DS unit 36. As another example, the DSmanaging unit 18 may indicate that like slice numbers of different datasegments are to be stored in the same DS unit 36. For example, the firstslice of each of the data segments is to be stored in a first DS unit36, the second slice of each of the data segments is to be stored in asecond DS unit 36, etc. In this manner, the data is encoded anddistributedly stored at physically diverse locations to improved datastorage integrity and security. Further examples of encoding the datasegments will be provided with reference to one or more of FIGS. 2-12.

Each DS unit 36 that receives a slice 42-48 for storage translates thevirtual DSN memory address of the slice into a local physical addressfor storage. Accordingly, each DS unit 36 maintains a virtual tophysical memory mapping to assist in the storage and retrieval of data.

The first type of user device 12 performs a similar function to storedata in the DSN memory 22 with the exception that it includes the DSprocessing. As such, the device 12 encodes and slices the data fileand/or data block it has to store. The device then transmits the slices11 to the DSN memory via its DSN interface 32 and the network 24.

For a second type of user device 14 to retrieve a data file or datablock from memory, it issues a read command via its interface 30 to theDS processing unit 16. The DS processing unit 16 performs the DSprocessing 34 to identify the DS units 36 storing the slices of the datafile and/or data block based on the read command. The DS processing unit16 may also communicate with the DS managing unit 18 to verify that theuser device 14 is authorized to access the requested data.

Assuming that the user device is authorized to access the requesteddata, the DS processing unit 16 issues slice read commands to at least athreshold number of the DS units 36 storing the requested data (e.g., toat least 10 DS units for a 16/10 error coding scheme). Each of the DSunits 36 receiving the slice read command, verifies the command,accesses its virtual to physical memory mapping, retrieves the requestedslice, or slices, and transmits it to the DS processing unit 16.

Once the DS processing unit 16 has received a read threshold number ofslices for a data segment, it performs an error decoding function andde-slicing to reconstruct the data segment. When Y number of datasegments has been reconstructed, the DS processing unit 16 provides thedata file 38 and/or data block 40 to the user device 14. Note that thefirst type of user device 12 performs a similar process to retrieve adata file and/or data block.

The transaction unit 21 may include DS processing 34 to communicateslices 47 with the DSN memory 22. The transaction unit 21 may initiatethe retrieval of a data file or data block from DSN memory 22 byidentifying the DS units 36 storing the slices of the data file and/ordata block 22. The transaction unit 21 then issues slice read commandsto at least a threshold number of the DS units 36 storing the requesteddata (e.g., to at least 10 DS units for a 16/10 error coding scheme).Each of the DS units 36 receiving the slice read command, verifies thecommand, accesses its virtual to physical memory mapping, retrieves therequested slice, or slices, and sends the slice(s) to the transactionunit 16. Once the transaction unit 21 has received a threshold number(k) of slices for a data segment, it performs a de-slicing and errordecoding function to reconstruct the data segment. The method repeatsfor a plurality of data segments that correspond to the data file. WhenY number of data segments has been reconstructed, the transaction unit21 processes a transaction based on the data file 38 and/or data block40. For example, the transaction unit 21 creates processed data toauthorize or complete a financial transaction based on the retrieveddata file 38 and/or data block 40 (e.g., that includes card data 17).The transaction unit 21 may store the processed data in the DSN memory.As such, the transaction unit 21 encodes and slices the processed datafile and/or data block and sends, via the DSN interface 32, the slices47 to the DS units 36 for storage therein.

The storage integrity processing unit 20 performs the third primaryfunction of data storage integrity verification. In general, the storageintegrity processing unit 20 periodically retrieves slices 45, and/orslice names, of a data file or data block of a user device to verifythat one or more slices have not been corrupted or lost (e.g., the DSunit failed). The retrieval process mimics the read process previouslydescribed.

If the storage integrity processing unit 20 determines that one or moreslices is corrupted or lost, it rebuilds the corrupted or lost slice(s)in accordance with the error coding scheme. The storage integrityprocessing unit 20 stores the rebuild slice, or slices, in theappropriate DS unit(s) 36 in a manner that mimics the write processpreviously described.

FIG. 2 is a schematic block diagram of an embodiment of a computing core26 that includes a processing module 50, a memory controller 52, mainmemory 54, a video graphics processing unit 55, an input/output (IO)controller 56, a peripheral component interconnect (PCI) interface 58,at least one IO device interface module 62, a read only memory (ROM)basic input output system (BIOS) 64, and one or more memory interfacemodules. The memory interface module(s) includes one or more of auniversal serial bus (USB) interface module 66, a host bus adapter (HBA)interface module 68, a network interface module 70, a flash interfacemodule 72, a hard drive interface module 74, and a DSN interface module76. Note the DSN interface module 76 and/or the network interface module70 may function as the interface 30 of the user device 14 of FIG. 1.Further note that the TO device interface module 62 and/or the memoryinterface modules may be collectively or individually referred to as TOports.

The processing module 50 may be a single processing device or aplurality of processing devices. Such a processing device may be amicroprocessor, micro-controller, digital signal processor,microcomputer, central processing unit, field programmable gate array,programmable logic device, state machine, logic circuitry, analogcircuitry, digital circuitry, and/or any device that manipulates signals(analog and/or digital) based on hard coding of the circuitry and/oroperational instructions. The processing module 50 may have anassociated memory and/or memory element, which may be a single memorydevice, a plurality of memory devices, and/or embedded circuitry of theprocessing module 50. Such a memory device may be a read-only memory,random access memory, volatile memory, non-volatile memory, staticmemory, dynamic memory, flash memory, cache memory, and/or any devicethat stores digital information. Note that if the processing module 50includes more than one processing device, the processing devices may becentrally located (e.g., directly coupled together via a wired and/orwireless bus structure) or may be distributedly located (e.g., cloudcomputing via indirect coupling via a local area network and/or a widearea network). Further note that when the processing module 50implements one or more of its functions via a state machine, analogcircuitry, digital circuitry, and/or logic circuitry, the memory and/ormemory element storing the corresponding operational instructions may beembedded within, or external to, the circuitry comprising the statemachine, analog circuitry, digital circuitry, and/or logic circuitry.Still further note that, the memory element stores, and the processingmodule 50 executes, hard coded and/or operational instructionscorresponding to at least some of the steps and/or functions illustratedin FIGS. 1-12.

FIG. 3 is a schematic block diagram of an embodiment of a dispersedstorage (DS) processing module 34 of user device 12 and/or of the DSprocessing unit 16. The DS processing module 34 includes a gatewaymodule 78, an access module 80, a grid module 82, and a storage module84. The DS processing module 34 may also include an interface 30 and theDSnet interface 32 or the interfaces 68 and/or 70 may be part of user 12or of the DS processing unit 14. The DS processing module 34 may furtherinclude a bypass/feedback path between the storage module 84 to thegateway module 78. Note that the modules 78-84 of the DS processingmodule 34 may be in a single unit or distributed across multiple units.

In an example of storing data, the gateway module 78 receives anincoming data object that includes a user ID field 86, an object namefield 88, and the data field 40 and may also receive correspondinginformation that includes a process identifier (e.g., an internalprocess/application ID), metadata, a file system directory, a blocknumber, a transaction message, a user device identity (ID), a dataobject identifier, a source name, and/or user information. The gatewaymodule 78 authenticates the user associated with the data object byverifying the user ID 86 with the managing unit 18 and/or anotherauthenticating unit.

When the user is authenticated, the gateway module 78 obtains userinformation from the management unit 18, the user device, and/or theother authenticating unit. The user information includes a vaultidentifier, operational parameters, and user attributes (e.g., userdata, billing information, etc.). A vault identifier identifies a vault,which is a virtual memory space that maps to a set of DS storage units36. For example, vault 1 (i.e., user 1's DSN memory space) includeseight DS storage units (X=8 wide) and vault 2 (i.e., user 2's DSN memoryspace) includes sixteen DS storage units (X=16 wide). The operationalparameters may include an error coding algorithm, the width n (number ofpillars X or slices per segment for this vault), a read threshold T, awrite threshold, an encryption algorithm, a slicing parameter, acompression algorithm, an integrity check method, caching settings,parallelism settings, and/or other parameters that may be used to accessthe DSN memory layer.

The gateway module 78 uses the user information to assign a source name35 to the data. For instance, the gateway module 60 determines thesource name 35 of the data object 40 based on the vault identifier andthe data object. For example, the source name may contain a fileidentifier (ID), a vault generation number, a reserved field, and avault identifier (ID). As another example, the gateway module 78 maygenerate the file ID based on a hash function of the data object 40.Note that the gateway module 78 may also perform message conversion,protocol conversion, electrical conversion, optical conversion, accesscontrol, user identification, user information retrieval, trafficmonitoring, statistics generation, configuration, management, and/orsource name determination.

The access module 80 receives the data object 40 and creates a series ofdata segments 1 through Y 90-92 in accordance with a data storageprotocol (e.g., file storage system, a block storage system, and/or anaggregated block storage system). The number of segments Y may be chosenor randomly assigned based on a selected segment size and the size ofthe data object. For example, if the number of segments is chosen to bea fixed number, then the size of the segments varies as a function ofthe size of the data object. For instance, if the data object is animage file of 4,194,304 eight bit bytes (e.g., 33,554,432 bits) and thenumber of segments Y=131,072, then each segment is 256 bits or 32 bytes.As another example, if segment sized is fixed, then the number ofsegments Y varies based on the size of data object. For instance, if thedata object is an image file of 4,194,304 bytes and the fixed size ofeach segment is 4,096 bytes, the then number of segments Y=1,024. Notethat each segment is associated with the same source name.

The grid module 82 receives the data segments and may manipulate (e.g.,compression, encryption, cyclic redundancy check (CRC), etc.) each ofthe data segments before performing an error coding function of theerror coding dispersal storage function to produce a pre-manipulateddata segment. After manipulating a data segment, if applicable, the gridmodule 82 error encodes (e.g., Reed-Solomon, Convolution encoding,Trellis encoding, etc.) the data segment or manipulated data segmentinto X error coded data slices 42-44.

The value X, or the number of pillars (e.g., X=16), is chosen as aparameter of the error coding dispersal storage function. Otherparameters of the error coding dispersal function include a readthreshold T, a write threshold W, etc. The read threshold (e.g., T=10,when X=16) corresponds to the minimum number of error-free error codeddata slices required to reconstruct the data segment. In other words,the DS processing module 34 can compensate for X-T (e.g., 16−10=6)missing error coded data slices per data segment. The write threshold Wcorresponds to a minimum number of DS storage units that acknowledgeproper storage of their respective data slices before the DS processingmodule indicates proper storage of the encoded data segment. Note thatthe write threshold is greater than or equal to the read threshold for agiven number of pillars (X).

For each data slice of a data segment, the grid module 82 generates aunique slice name 37 and attaches it thereto. The slice name 37 includesa universal routing information field and a vault specific field and maybe 48 bytes (e.g., 24 bytes for each of the universal routinginformation field and the vault specific field). As illustrated, theuniversal routing information field includes a slice index, a vault ID,a vault generation, and a reserved field. The slice index is based onthe pillar number and the vault ID and, as such, is unique for eachpillar (e.g., slices of the same pillar for the same vault for anysegment will share the same slice index). The vault specific fieldincludes a data name, which includes a file ID and a segment number(e.g., a sequential numbering of data segments 1-Y of a simple dataobject or a data block number).

Prior to outputting the error coded data slices of a data segment, thegrid module may perform post-slice manipulation on the slices. Ifenabled, the manipulation includes slice level compression, encryption,CRC, addressing, tagging, and/or other manipulation to improve theeffectiveness of the computing system.

When the error coded data slices of a data segment are ready to beoutputted, the grid module 82 determines which of the DS storage units36 will store the EC data slices based on a dispersed storage memorymapping associated with the user's vault and/or DS storage unit 36attributes. The DS storage unit attributes may include availability,self-selection, performance history, link speed, link latency,ownership, available DSN memory, domain, cost, a prioritization scheme,a centralized selection message from another source, a lookup table,data ownership, and/or any other factor to optimize the operation of thecomputing system. Note that the number of DS storage units 36 is equalto or greater than the number of pillars (e.g., X) so that no more thanone error coded data slice of the same data segment is stored on thesame DS storage unit 36. Further note that EC data slices of the samepillar number but of different segments (e.g., EC data slice 1 of datasegment 1 and EC data slice 1 of data segment 2) may be stored on thesame or different DS storage units 36.

The storage module 84 performs an integrity check on the outboundencoded data slices and, when successful, identifies a plurality of DSstorage units based on information provided by the grid module. Thestorage module then outputs the encoded data slices 1 through X of eachsegment 1 through Y to the DS storage units. Each of the DS storageunits 36 stores its EC data slice(s) and maintains a local virtual DSNaddress to physical location table to convert the virtual DSN address ofthe EC data slice(s) into physical storage addresses.

In an example of a read operation, the user device 12 and/or 14 sends aread request to the DS processing unit 14, which authenticates therequest. When the request is authentic, the DS processing unit 14 sendsa read message to each of the DS storage units 36 storing slices of thedata object being read. The slices are received via the DSnet interface32 and processed by the storage module 84, which performs a parity checkand provides the slices to the grid module 82 when the parity check wassuccessful. The grid module 82 decodes the slices in accordance with theerror coding dispersal storage function to reconstruct the data segment.The access module 80 reconstructs the data object from the data segmentsand the gateway module 78 formats the data object for transmission tothe user device.

FIG. 4 is a schematic block diagram of an embodiment of a grid module 82that includes a control unit 73, a pre-slice manipulator 75, an encoder77, a slicer 79, a post-slice manipulator 81, a pre-slice de-manipulator83, a decoder 85, a de-slicer 87, and/or a post-slice de-manipulator 89.Note that the control unit 73 may be partially or completely external tothe grid module 82. For example, the control unit 73 may be part of thecomputing core at a remote location, part of a user device, part of theDS managing unit 18, or distributed amongst one or more DS storageunits.

In an example of write operation, the pre-slice manipulator 75 receivesa data segment 90-92 and a write instruction from an authorized userdevice. The pre-slice manipulator 75 determines if pre-manipulation ofthe data segment 90-92 is required and, if so, what type. The pre-slicemanipulator 75 may make the determination independently or based oninstructions from the control unit 73, where the determination is basedon a computing system-wide predetermination, a table lookup, vaultparameters associated with the user identification, the type of data,security requirements, available DSN memory, performance requirements,and/or other metadata.

Once a positive determination is made, the pre-slice manipulator 75manipulates the data segment 90-92 in accordance with the type ofmanipulation. For example, the type of manipulation may be compression(e.g., Lempel-Ziv-Welch, Huffman, Golomb, fractal, wavelet, etc.),signatures (e.g., Digital Signature Algorithm (DSA), Elliptic Curve DSA,Secure Hash Algorithm, etc.), watermarking, tagging, encryption (e.g.,Data Encryption Standard, Advanced Encryption Standard, etc.), addingmetadata (e.g., time/date stamping, user information, file type, etc.),cyclic redundancy check (e.g., CRC32), and/or other data manipulationsto produce the pre-manipulated data segment.

The encoder 77 encodes the pre-manipulated data segment 92 using aforward error correction (FEC) encoder (and/or other type of erasurecoding and/or error coding) to produce an encoded data segment 94. Theencoder 77 determines which forward error correction algorithm to usebased on a predetermination associated with the user's vault, a timebased algorithm, user direction, DS managing unit direction, controlunit direction, as a function of the data type, as a function of thedata segment 92 metadata, and/or any other factor to determine algorithmtype. The forward error correction algorithm may be Golay,Multidimensional parity, Reed-Solomon, Hamming, Bose Ray ChauduriHocquenghem (BCH), Cauchy-Reed-Solomon, or any other FEC encoder. Notethat the encoder 77 may use a different encoding algorithm for each datasegment 92, the same encoding algorithm for the data segments 92 of adata object, or a combination thereof.

The encoded data segment 94 is of greater size than the data segment 92by the overhead rate of the encoding algorithm by a factor of X/T, whereX is the width or number of slices, and T is the read threshold. In thisregard, the corresponding decoding process can accommodate at most X-Tmissing EC data slices and still recreate the data segment 92. Forexample, if X=16 and T=10, then the data segment 92 will be recoverableas long as 10 or more EC data slices per segment are not corrupted.

The slicer 79 transforms the encoded data segment 94 into EC data slicesin accordance with the slicing parameter from the vault for this userand/or data segment 92. For example, if the slicing parameter is X=16,then the slicer slices each encoded data segment 94 into 16 encodedslices.

The post-slice manipulator 81 performs, if enabled, post-manipulation onthe encoded slices to produce the EC data slices. If enabled, thepost-slice manipulator 81 determines the type of post-manipulation,which may be based on a computing system-wide predetermination,parameters in the vault for this user, a table lookup, the useridentification, the type of data, security requirements, available DSNmemory, performance requirements, control unit directed, and/or othermetadata. Note that the type of post-slice manipulation may includeslice level compression, signatures, encryption, CRC, addressing,watermarking, tagging, adding metadata, and/or other manipulation toimprove the effectiveness of the computing system.

In an example of a read operation, the post-slice de-manipulator 89receives at least a read threshold number of EC data slices and performsthe inverse function of the post-slice manipulator 81 to produce aplurality of encoded slices. The de-slicer 87 de-slices the encodedslices to produce an encoded data segment 94. The decoder 85 performsthe inverse function of the encoder 77 to recapture the data segment90-92. The pre-slice de-manipulator 83 performs the inverse function ofthe pre-slice manipulator 75 to recapture the data segment.

FIG. 5 is a diagram of an example of slicing an encoded data segment 94by the slicer 79. In this example, the encoded data segment includesthirty-two bits, but may include more or less bits. The slicer 79disperses the bits of the encoded data segment 94 across the EC dataslices in a pattern as shown. As such, each EC data slice does notinclude consecutive bits of the data segment 94 reducing the impact ofconsecutive bit failures on data recovery. For example, if EC data slice2 (which includes bits 1, 5, 9, 13, 17, 25, and 29) is unavailable(e.g., lost, inaccessible, or corrupted), the data segment can bereconstructed from the other EC data slices (e.g., 1, 3 and 4 for a readthreshold of 3 and a width of 4).

FIG. 6 is a flowchart illustrating the determination of a disguisedslice name 110 by processing module of the DS processing such that thefile ID is not transparent in the data name portion of the slice name.The method begins with the step where the processing module receives theuser ID 86, object name 88, and data object 40 (e.g., for a store to theDSN scenario). The method continues at step 100 where the processingmodule determines the source name 108 such that a new file ID is createdif one does not already exist for this user and object name. Theprocessing module checks a user vault for this user to determine if theobject name is affiliated with a previously assigned file ID. If so, theprocessing module utilizes the same file ID and if not, the processingmodule creates a new file ID and saves the new file ID in the user vaultfor this user. The processing module may create the file ID as one ormore of a random number, an encryption operation of the object name,and/or a hash operation (e.g., cyclic redundancy check) of the objectname. Note that the source name is the same for every slice of the samedata object. The processing module creates one or more data segmentsbased on the data object. The processing module encodes the data segmentin accordance with an error coding dispersed storage function to producea plurality of error coded data slices.

The method continues with step 102 where the processing module generatesa slice name for an error coded data slice of the plurality of errorcoded data slices, wherein the slice name includes a dispersed storagerouting information section and a data identification section. Note thatthe data identification section comprises identification of the datasegment and the data object, wherein the data segment is one of aplurality of data segments of the data object. Further note that theslice index is based on the pillar number and vault ID. Further notethat the data name is based on the file ID and segment number such thatthe data name is the same (e.g., when not disguised) in slice namesacross slices of the same segment.

The method continues with step 104 where the processing module performsa securing function on at least the data identification section toproduce a secure data identification section. Note that the securingfunction may include performing a deterministic mathematical function onsome portion or all of the slice name. Further note that thedeterministic mathematical function includes one or more of but notlimited to a hash function, encryption, adding/subtracting an offsetvalue, and scrambling. For example, the processing module performs thedeterministic mathematical function by encrypting a portion of thenon-disguised slice name utilizing an encryption key where theencryption key is a fixed key (e.g., retrieved from memory) or isderived from one or more elements of the slice name. In another example,the processing module calculates a hash (e.g., cyclic redundancy check)of non-disguised slice names. Note that the hash shall produce a resultthat may be at least as wide (e.g., in bytes) as the data name field(e.g., 24 bytes), and less than the slice name width (e.g., 48 bytes).For example, secure hash algorithm (SHA)-256 may be utilized to producea 32 byte result. Note that the hash function generates the same numberfor the same input but is difficult to produce the original number basedon the hash result. The processing module truncates the hash to the sizeof the data name field (e.g., 24 bytes).

The method continues with step 106 where the processing module replaces,within the slice name, the data identification section (e.g., the dataname) with the secure data identification section (e.g., the truncatedhashes) to produce a secure slice name. For example, the processingmodule replaces the data name field of the corresponding slice name withthe hash to produce a disguised slice name 110.

The method continues with the processing module generating a unique dataname for remaining ones of the plurality of error coded data slices toproduce a plurality of slice names. For example, the processing moduleadditionally secures the slice names for each of at least a pillar widthminus a decode threshold number of the plurality of slice names byperforming a securing function on at least the data identificationsection to produce a secure data identification section. Next, theprocessing module replaces the data identification section with thesecure data identification section. The disguised slice names 110 may beutilized to store and retrieve EC data slices from the DSN memory. Notethat the original object name is required to identify EC data slicesthat are formed from the same data segments and data object 40 in aretrieval sequence.

In an example of operation, the processing module processes an accessrequest to a data object where at least some of the slice names werepreviously secured utilizing the method described above. The methodbegins with the step where the processing module receives an accessrequest to a data object. The processing module determines one or morerequired data segments to reconstruct the data object wherein each datasegment is encoded in accordance with an error coding dispersed storagefunction to produce a plurality of error coded data slices that arestored in a plurality of DS storage units. The method continues with thestep where the processing module generates a slice name for an errorcoded data slice of the plurality of error coded data slices, whereinthe slice name includes a dispersed storage routing information sectionand a data identification section. The method continues with the stepwhere the processing module performs a securing function on at least thedata identification section to produce a secure data identificationsection. The processing module replaces, within the slice name, the dataidentification section with the secure data identification section toproduce a secure slice name. The method continues with the step wherethe processing module accesses the error coded slice based on the secureslice name. The method continues with the step where the processingmodule generates slice names for remaining ones of the plurality oferror coded data slices to produce a plurality of slice names. Theprocessing module secures the slice names to produce secure slice namesfor each of at least a decode threshold minus one number of theplurality of slice names by performing a securing function on at leastthe data identification section to produce a secure data identificationsection. Next, the processing module replaces the data identificationsection with the secure data identification section. The methodcontinues with the step where the processing module accesses theremaining ones of the plurality of error coded data slices based on thesecure slice names.

FIG. 7 is a flowchart illustrating the creation and storage of anauthorization request and the retrieval and processing of anauthorization request response 134 by a processing module of the userdevice (e.g., a point of sale terminal) and/or DS processing unit. Thesetwo steps may comprise the authorization sequence for a purchasingtransaction where a credit card is utilized to execute a purchase.

The method begins with step 120 where the processing module receivestransaction information 120 from one or more financial transactionapplications. For example, the processing module receives accountinformation regarding an electronic-commerce transaction. In aninstance, the processing module may execute a credit card transactionapplication implemented on the computing core of the point of saleterminal user device. The user device may have previously formed thetransaction information based on the credit card data, an amount of thetransaction (e.g., currency type and amount), a merchant identifier(e.g., a unique number associated with the merchant executing thetransaction), and a transaction number (e.g., a unique reference numberof the transaction).

The method continues with step 122 where the processing module createsan authorization request message by generating a transactionauthorization request message based on one or more of the accountinformation, the transaction information, and merchant information. Themethod continues with step 124 where the processing module determinesdispersal parameters to dispersedly store the authorization requestmessage in the DSN memory. The dispersal parameters may include theerror coding parameters, security parameters, whether to disguise theslice names (and the method), slice transmission ordering, whether toinject random slices (e.g., to confuse a hacker), and/or which DS unitsto send the slices to for storage therein. The dispersal parameters maybe assigned by the DS managing unit utilizing one or more scenarios ofat least a portion of a vault for the merchant, a vault for the cardholder, a vault for a card issuer, a vault for an authorization agent,and/or a vault for authorization requests. The processing moduledetermines which DS units to send the slices to with a store commandbased on the virtual DSN address (e.g., un-disguised slice name) tophysical location (DS unit) table, a vault assignment, and/or inaccordance with an authorization protocol. Note that the authorizationprotocol may indicate a plurality of DS units to be utilized to passinformation back and forth between a point-of-sale user device terminal12 and the transaction unit 21 or an authorization server.

The method continues with step 126 where the processing module encodesthe transaction authorization request message in accordance with anerror coding dispersed storage function to produce a plurality ofencoded data slices. The method continues in step 128 where theprocessing module outputs the plurality of encoded data slices to aplurality of dispersed storage units in accordance with theauthorization protocol. The processing module may send the slices as abatch to one DS unit at a time or may send one slice at a time todifferent DS units. In other words, the processing module may generate aplurality of write messages such that each write message includes aslice name and a corresponding error coded data slice. Note that theslice name includes dispersed storage routing information and atransaction name. Further note that the routing information identifiesdispersed storage units associated with the authorization server and thetransaction name identifies the transaction authorization requestmessage. Alternatively or in addition to outputting the plurality ofencoded data slices to a plurality of dispersed storage units, theprocessing module may output a message to the authorization serverregarding the transaction authorization request message in accordancewith the authorization protocol such that the authorization server maysubsequently (e.g., immediately) retrieve the plurality of encoded dataslices.

In addition, the processing module may embed the transactionauthorization request message (e.g., data content for secure datacontent transmission) into a data stream (e.g., wherein the data streamcomprises at least one of null data, at least one pre-defined data file,random data, calculated data based on one or more of accountinformation, transaction history information, and merchant information)to produce a stream of data. Next, the processing module sequentiallyencodes data segments of the stream of data in accordance with the errorcoding dispersed storage function to produce pluralities of encoded dataslices. The processing module outputs the pluralities of encoded dataslices to a plurality of dispersed storage units for storage therein.Note that sending the slices as described above, even if over a commonlink to the network, improves the security of the system.

The transaction unit 21 periodically retrieves slices for the sameobject name from the same DS units that the processing module utilizedas described in the method above to store the authorization requestmessage. The transaction unit creates an authorization request responseand stores it in the DSN memory for the user device (e.g., point of saleterminal) to retrieve. The method of the transaction unit 21 isdescribed in greater detail with reference to FIG. 8.

The method continues with step 130 and the processing module retrievesat least a threshold number of encoded data response slices from theplurality of dispersed storage units and decodes the message. Theprocessing module generates a plurality of read messages and sends theplurality of read messages to the DS units in accordance with theauthorization protocol (e.g., which DS units). Note that each readmessage includes a slice name such that the slice name includesdispersed storage routing information and a transaction response name.Further note that the dispersed storage routing information identifiesdispersed storage units associated with an authorization server (e.g.,the transaction unit 21), and the transaction response name identifiesthe response message. The processing module receives at least athreshold number of encoded data response slices from the plurality ofdispersed storage units in accordance with the authorization protocol.The processing module decodes the plurality of encoded data responseslices in accordance with the error coding dispersed storage function toproduce a response message.

The method continues with step 132 where the processing moduledetermines if the decoded message contains an authorization requestresponse for this transaction. The method repeats back to step 130 theprocessing module determines that the message is not the authorizationrequest response for this transaction. The method continues to the nextstep when the processing module determines that the message is theauthorization request response for this transaction.

The method continues with step 136 where the processing moduledetermines the authorization request response type when the processingmodule determines that the response has been decoded. The processingmodule determines the authorization request response type based on acomparison of the response to a list of potential responses. The methodends with step 140 where the processing module provides a denialnotification when the processing module determines that theauthorization request response type is a denial message. The denialnotification may include a visual indicator and/or a message provided tothe financial transaction such that the message indicates the denialnotification. The method continues to the next step when the processingmodule determines that the authorization request response type is anapproval type.

In the next step 142, the processing module provides an approvalnotification when the DS processing unit determines the response type asan approval. The approval notification may include a visual indicatorand/or a message provided to the financial transaction where the messageindicates the approval notification. Note that the financial transactionapplication may complete the sale and the merchant would release thegoods and/or services.

The method continues with step 144 where the processing module appendsthe approval to the transaction information to form authorizedtransaction information. The processing module caches the authorizedtransaction information such that the processing module may subsequently(e.g., at the end of the day) create a settlement request and process itbased on the authorized transaction information. The settlement requestis discussed in greater detail with reference to FIGS. 9-10.

FIG. 8 is a flowchart illustrating the retrieval and processing of anauthorization request and the creation and storage of an authorizationrequest response by the transaction unit 21. These two steps maycomprise the authorization sequence for a purchasing transaction where acredit card is utilized to execute a purchase.

The transaction unit determines dispersal parameters 150 to retrieve thedistributed authorization request message from the DSN memory. Thedispersal parameters may include the error coding parameters, securityparameters, if the slice names are disguised (and the method), slicetransmission ordering, whether random slices may exist, and/or the DSunits to retrieve the slices 152 from. The dispersal parameters may beassigned by the DS managing unit utilizing one or more scenarios of atleast a portion of a vault for the merchant, a vault for the cardholder, a vault for a card issuer, a vault for an authorization agent,and/or a vault for authorization requests. The transaction unitdetermines the object name for the authorization request. The objectname may be pre-determined or distributed periodically by a unit of thesystem (e.g., the DS managing unit). The transaction unit determineswhich DS units to retrieve the slices from with the retrieve commandbased on the virtual DSN address (e.g., un-disguised slice name) tophysical location (DS unit) table and the vault assignment for thisscenario.

The transaction unit retrieves the slices and re-creates theauthorization request 154 by de-slicing and decoding the slices. Thetransaction unit determines the account ID based on the authorizationrequest (e.g., part of the transaction information). The transactionunit determines the dispersal parameters associated with the storage ofaccount information (e.g., credit limits, transaction history, creditcard account balance) for the account ID 156. The account informationmay be in a vault linked to one or more of the account holder, the cardissuer, an authorizing agent, and/or a vault for account information.

The transaction unit retrieves the slices for the account information ofthe account ID 158. The transaction unit re-creates the accountinformation 160 by de-slicing and decoding the slices. The transactionunit determines if a comparison of the authorization request to theaccount information is favorable 162. The determination may be based onone or more of the current account balance, the credit limit, the amountof the transaction, the type of purchase, and/or the location of thepurchase. For example, the comparison is favorable 164 when the currentbalance plus the transaction amount is less than the credit limit.

The transaction unit creates a denial message when the comparison of theauthorization request to the account information is not favorable. Thetransaction unit generates the denial authorization request responsemessage 166. The transaction unit determines the object name, slicenames, and DS unit locations associated with the response. Thetransaction unit creates and sends slices of the response for storage inthe DSN memory 170. Note that the user device retrieves the responsemessage from these slices as described with reference to FIG. 7.

The transaction unit updates the account information (e.g., replaces theaccount balance with the transaction amount and the old account balance)when the comparison of the authorization request to the accountinformation is favorable 162. The transaction unit creates and sendsslices with the store command to the DSN 170 units (e.g., as determinedpreviously for the account information) based on the updated accountinformation. The transaction unit creates the approved authorizationrequest response message 172. The transaction unit determines the objectname, slice names, and DS unit locations associated with the response.The transaction unit creates and sends slices of the response forstorage in the DSN 174 memory. Note that the user device retrieves theresponse message from these slices as described with reference to FIG.7.

FIG. 9 is a flowchart illustrating the creation and storage of asettlement request by the user device (e.g., a point of sale terminal)and/or DS processing unit. This method may be utilized to complete thesettlement of a previously authorized transaction.

The DS processing unit determines if it's time to aggregate authorizedtransaction information 180 that was previously cached by the userdevice and/or DS processing unit. The determination may be based onexecuting the aggregation from time to time, in response to a request,and/or any time settlements are desired.

The DS processing unit aggregates the authorized transaction informationinto a settlement request 184. The aggregation may include one or moreauthorized transaction information sets (e.g., from one or moretransactions). The DS processing unit determines the dispersalparameters for the settlement request that mimics the determination ofthe dispersal parameters 186 for the authorization request. Thedispersal parameters for the settlement request may utilize a differentobject name to differentiate it from the authorization request.

The DS processing unit creates the slices 188 based on the settlementrequest and dispersal parameters. The DS processing unit determines ifit is time to send a slice with a store command 190. The DS processingunit may send 192 a portion of the slices at any one time to furtherenhance the security of the system. The determination to send may bebased on one or more of a time schedule, a priority indicator, asecurity indicator, and/or any other indicator to improve the securityof the system. The DS processing unit sends the slice and store command194 to the DS unit when the DS processing unit determines it is time tosend a slice.

The DS processing unit determines if it is done 196 sending all theslices. The DS processing unit returns to determine if it is time tosend a slice when it is not done 196 sending slices. The DS processingunit returns to determine if it is time to aggregate authorizationtransaction information when it is done 196 sending slices.

FIG. 10 is a flowchart illustrating the retrieval and processing of asettlement request by the transaction unit. This method may be utilizedto complete the settlement of a previously authorized transaction.

The transaction unit determines if it is time to process authorizedtransaction information 200. The determination may be based on one ormore of a time period elapsing since the last processing, a request, anactivity indicator, and/or any other stimulus that may invoke theprocessing.

The transaction unit determines the dispersal parameters when thetransaction unit determines it is time to process authorized transactioninformation 200. The determination may mimic that previously discussedwhen the user device determined the dispersal parameters 204 to storethe settlement request in the DSN memory. The transaction unit retrievesthe slices 206 from the DS units, de-slices, and decodes the authorizedtransaction information and settlement request in accordance with thedispersal parameters.

The transaction unit determines the account ID based on the settlementrequest (e.g., part of the transaction information). The transactionunit determines the dispersal parameters 204 associated with the storageof account information (e.g., credit limits, transaction history, creditcard account balance) for the account ID. The account information may bein a vault linked to one or more of the account holder, the card issuer,an authorizing agent, and/or a vault for account information.

The transaction unit retrieves the slices for the account information ofthe account ID 214. The transaction unit re-creates the accountinformation 216 by de-slicing and decoding the slices. The transactionunit updates the account information 218 (e.g., debits the newauthorized transaction to the outstanding balance due) by creating andsending slices with the store command to the DSN units 220 (e.g., asdetermined previously for the account information). Note that in asimilar fashion the transaction unit may create a credit message (e.g.,containing the merchant ID, amount, transaction number), determinedispersal parameters unique to sending the credit message, create theslices, and send the slices with a store command to the DSN memory.

FIG. 11 is a flowchart illustrating the retrieval of account informationwhere a processing module of the transaction unit and/or DS processingunit may control the access to account information. The accountinformation is previously stored in the DSN memory and may includethousands and even millions of records containing the accountidentifiers (e.g., credit card numbers), credit limits, accountbalances, security information, card holder name, card holder address,card holder social security numbers, and other card holder personalinformation.

The transaction unit receives an access request to retrieve accountinformation 240 from a requester (e.g., a user device or any otherentity that is not authorized to directly access the DSN memory any maynot have the necessary dispersal information to acquire the distributeddata containing account information). The access request may include oneor more of a requester ID, requester credentials (e.g., a public keysigned certificate, and/or a login and password), and/or the accountinformation identifier(s) (ID).

The transaction unit determines access constraints 242 based on theaccount information ID. The determination may be based on retrieving theaccess constraints from the DSN memory for the account ID and/orretrieving the access constraints from the DSN memory for multipleaccounts (e.g., constraints for accounts of the same card issuer orother similarity).

The access constraints specify acceptable scenarios for access to theaccount information and may include one or more of a list of authorizedrequesters, authorized requester credentials, which portions of theaccount information are accessible, restrictions on the maximum volumeof account information (e.g., only access one thousand records at atime), restrictions on the minimum time between accessing the differentportions of the account information (e.g., 60 minutes must pass betweenretrieving blocks of 1000 records), and/or the access history.

The transaction unit determines if the access request compares favorablywith the access constraints 244. For example, a favorable 246 comparisonis determined if the requester ID and requester credential match theauthorized requester and authorized requester credentials (e.g.,retrieved from the access constraints) and the account informationrequested is less than the maximum volume and the access historyindicates that time since the last access is greater than the minimumtime between accessing the account information constraint.

The transaction unit sends a denial access request response 248 to therequester when the transaction unit determines that the access requestdoes not compare favorably with the access constraints.

The transaction unit determines the dispersal parameters 250, retrievesthe slices 252, decodes the data and re-creates the account information254 when the transaction unit determines that the access requestcompares favorably with the access constraints.

The transaction unit sends a portion of the account information to therequester 256. The portion may be limited by the access constraints insize and frequency of sending portions. For example, the request may befor account information records for ten thousand account IDs but theaccess constraints limit the transfers to the requester to five hundredrecords in one portion and the portions must be spaced apart by at leastthirty minutes.

The transaction unit may check for further requests to retrieve accountinformation when the last portion sent completed the request. Thetransaction unit may determine if the portion(s) of account informationsent so far compares favorably to the access constraints 260 when thelast portion sent did not complete the request. For example, anunfavorable comparison may exist when the proper amount of time may nothave elapsed since the last portion was sent to allow sending the nextportion. In another example of an unfavorable comparison, the requesterID may not be allowed to access more account information. Note that insuch a fatal scenario the process may stop. The transaction unit willcontinue to check the conditions when the comparison is not favorable262 (e.g., and not fatal).

The transaction unit may update the access constraints 246 when thetransaction unit determines if the portion(s) of account informationsent so far compares favorably to the access constraints. For example,the update increments the tracking of the portions of the accountinformation sent and at what time. The transaction unit continues tosend the next portion of the account information to the requester.

FIG. 12 is a flowchart illustrating the retrieval of information wherethe DS unit and/or DS processing may control the access to slicescontaining account information. The account information is previouslystored in the DSN unit.

The DS unit receives a retrieval request to retrieve a slice 270 from arequester (e.g., a user device or any other entity). The retrievalrequest may include one or more of a slice name, a requester ID,requesting device ID, requester credentials (e.g., a public key signedcertificate, and/or a login and password), and/or the accountinformation identifier(s) (ID).

The DS unit determines local access constraints 272 based on the slicename. The determination may be based on retrieving the local accessconstraints from DS unit memory and/or the DSN memory for the slicename. Slices may be tracked that are affiliated with each other (e.g.,slices of the same segment, block, or file) such that limits are placedon accessing affiliated slices.

The local access constraints specify acceptable scenarios for access tothe slice and may include one or more of a list of authorized requestersand devices, authorized requester credentials, which slices areaccessible, restrictions on the maximum volume of slices (e.g., onlyaccess one thousand slices at a time), restrictions on the minimum timebetween accessing affiliated slices (e.g., 60 minutes must pass betweenretrieving 1000 slices that affiliated to the same data object), and/orthe access history.

The DS unit determines if the retrieval request compares favorably withthe local access constraints 274. For example, a favorable 276comparison is determined if the device ID and requester credential matchthe authorized requester and authorized requester credentials (e.g.,retrieved from the local access constraints) and the number of slicesrequested is less than the maximum volume and the access historyindicates that time since the last retrieval is greater than the minimumtime between accessing the slices (e.g., affiliated slices).

The DS unit sends a denial retrieval request response 278 to therequester when the DS unit determines that the retrieval request doesnot compare favorably with the local access constraints.

The DS unit retrieves the slice 280 when the DS unit determines that theretrieval request compares favorably with the local access constraints.The DS unit sends the slice to the requester 282. The DS unit may updatethe local access constraints 284. For example, the update increments thetracking of slices sent and at what time. Slices may be tracked that areaffiliated with each other (e.g., slices of the same segment, block, orfile).

FIG. 13 is a flowchart illustrating secure access of dispersedly storeddata by a processing module. The processing module may be implemented ina user device, a DS processing unit, a DS managing unit, a storageintegrity processing unit, the transaction unit, and/or a DS unit. Forexample, the processing module is implemented in the user device. Themethod begins with step 286 where the processing module generates arequest to access secure data. The secure data may include sensitiveinformation that should only be accessed by authorized entities. Thesecure data may include one or more of but not limited to financialaccount information including credit card information, savings accountinformation, checking account information, historical records,retirement account information, stock transaction information, andcredit information. The request includes a user identification code (ID)and at least one object name for the secure data. The secure data mayinclude one or more of but not limited to financial account information,user password information, security credential information, and personaldata.

The method continues with step 288 where the processing module transmitsthe request to a first dispersed storage network (DSN) access portal.The DSN access portal may include one or more DS units, and/or a DSprocessing unit of a particular DSN system. Note that the processingmodule may determine one or more DSN access portals to access areconstruction threshold number of coded data slices to reconstruct therequested secured data. The determination is based on one or more of butnot limited to a user ID, a vault ID, a vault lookup, apredetermination, a command, and a message.

The method continues with step 290 where the processing module receivesa first response from the first DSN access portal. The first responseincludes, for a data segment of the secure data, a first set of encodeddata slices, wherein the first set of encoded data slices includes lessthan a reconstruction threshold number of encoded data slices. Note thatthe first response is based on a security level associated with the userID and security parameters of the secure data. The security parametersmay include one or more of but not limited to a secrecy level of data,an amount of data, encryption information regarding the data, codecinformation regarding the data, and error coding dispersal storagefunction parameters. The method of the DSN access portal to determinethe first response is discussed in greater detail with reference to FIG.14.

The method continues with step 292 where the processing module generatesa second request to access the secure data in response to receiving thefirst response. The second request includes the user ID and the at leastone object name for the secure data. In addition, the second request mayinclude a representation of the first response. The representation mayinclude a list of slices received so far, required slices, the firstresponse, a summary of the first response, and/or a DSN access portalidentifier. For example, the second request may include slice names ofthe encoded data slices received in the first response. The methodcontinues with step 294 where the processing module transmits the secondrequest to a second DSN access portal.

The method continues with step 296 when the processing module receives asecond response from the second DSN access portal. The second responseincludes, for the data segment of the secure data, a second set ofencoded data slices, wherein the second set of the encoded data slicesincludes less than the reconstruction threshold number of encoded dataslices. The second response is based on the security level associatedwith the user ID, the first response, and the security parameters of thesecure data. For example, the second response may include the remainingrequired encoded data slices to reconstruct the data segment when thesecurity level associated with the user ID is favorable (e.g., a verytrusted user ID) and/or when the security parameters of the secure datais favorable (e.g., a low security risk).

The method continues with step 298 where the processing moduledetermines if a reconstruction threshold number of encoded data sliceshave been received (e.g., by comparing the number of received slices tothe reconstruction threshold number). The method continues to step 300where the processing module obtains more encoded data slices. Theprocessing module obtains more encoded data slices in a similar manneras described above where the processing module generates a third or morerequest to access secure data and transmits the third or more requeststo access secure data to a third or more DSN access portals. Theprocessing module receives a third or more responses from the third ormore DSN the access portals. The method repeats back to step 298 wherethe processing module determines if a reconstruction threshold number ofencoded data slices have been received. The method continues to step 302when the processing module determines that enough (e.g. a reconstructionthreshold number) of encoded data slices have been received. The methodcontinues with step 302 where the processing module decodes the encodeddata slices to reconstruct the data (e.g., one or more data segments ofthe secure data).

FIG. 14 is another flowchart illustrating secure access of dispersedlystored data by a processing module. The processing module may beimplemented in a user device, a DS processing unit, a DSN access portal,a DS managing unit, a storage integrity processing unit, the transactionunit, and/or a DS unit. Note that the DSN access portal may beimplemented in a DS processing unit as an interface between the userdevice and one or more DSN memories. For example, the processing moduleis implemented in the DS processing unit. The method begins with step304 where the processing module receives a request from a user device toaccess secure data. Alternatively, the request may be received from theDS processing unit, the DS managing unit, storage integrity processingunit, the transaction unit, and/or a DS unit. The request includes auser identification code (ID) and at least one object name (e.g., filename, block ID) for the secure data.

The method continues with step 306 where the processing moduledetermines a security level associated with the user device. Thedetermination may be based on one or more of but not limited to the userID, communicating with the DS managing unit to obtain and/or verify thesecurity level associated with the user device, a vault lookup, acommand, a predetermination, and a message. For example, the processingmodule communicates with the DS managing unit to retrieve a securitylevel of three (of ten) that is associated with the user ID. In aninstance, the security level of three of ten indicates that user ID doesnot have broad access to secure data. In another instance, a securitylevel of ten of ten indicates that the user ID has broad access tosecure data.

The method continues with step 308 where the processing moduledetermines security parameters associated with the secure data. Thedetermination may be based on one or more of but not limited to thesecure data, the object name, communicating with the DS managing unit toobtain and/or verify the security parameters associated with the securedata, a secrecy level of data, an amount of data, codec informationregarding the data, error coding dispersal storage function parameters,a vault lookup, a command, a predetermination, and a message. Forexample, the processing module communicates with the DS managing unit toretrieve a security parameter of three (of ten) that is associated withthe secure data. In an instance, the security parameter of three of tenindicates that access to the secure data is not very restricted. Inanother instance, a security parameter of ten of ten indicates thataccess to the secure data is very restricted.

The method continues with step 310 where the processing moduledetermines a level of access to the secure data. The determination isbased on one or more of but not limited to the user ID, object name, thesecurity level associated with the user device, the security parametersassociated with the secure data, a vault lookup, a predetermination, acommand, and a message. For example, the processing module determinesthe level of access to be partial (e.g., less than a reconstructionthreshold number of slices will be provided to the requester) when thesecurity parameters are greater than the security level. In anotherexample, the processing module determines the level of access be full(e.g., at least a reconstruction threshold number of slices will beprovided to the requester) when the security level is greater thansecurity parameters.

The method continues with step 312 where the processing moduledetermines if the request is missing a representation of a response fromanother DSN access portal when the request is not a first request. Inother words, the processing module determines whether the requestincludes the representation of a response from another computing deviceand when the request does not include the representation, the processingmodule determines whether the request is the first request. Note thatthe representation of the response from another DSN access portal (e.g.,a computing device) may indicate how many slices (e.g., which slicenames) have been previously retrieved from one or more different DSNaccess portals. Note that the request may further include an indicatorof how many DSN access portals have been accessed to access the securedata. In an instance, the indicator may be zero when the request is thefirst request.

The method branches to step 316 when the processing module determinesthat the request is not missing a representation of the response fromanother DSN access portal when the request is not the first request.Note that the method always branches to step 316 when the request is thefirst request. The method continues to step 314 when the processingmodule determines that the request is missing the representation of theresponse from another DSN access portal when the request is not thefirst request. The method ends with step 314 where the processing modulegenerates a deny request message. The message may include one or more ofbut not limited to the request, the user ID, a DSN access portalidentifier, the security level associated with the user device, thesecurity parameters associated with the secure data, the level ofaccess, a denial reason indicator, and a command. In addition, theprocessing module may send the deny request message to the requester(e.g. the user device) and/or the DS managing unit.

When the processing module determines that the request is not missing arepresentation of the response from another DSN access portal when therequest is not the first request, the method continues with step 316where the processing module determines a number of encoded data slices(a set) when the access level is partial (e.g., less than a constructionthreshold number). The determination of the number of slices of a set ofencoded data slices to include it is based on one or more of but notlimited to a variable function of the security parameters and thesecurity level associated with the user ID, the user ID, the objectname, the security parameters, the security level, the level of access,a vault lookup, a predetermination, a message, and a command. Forexample, the processing module may determine to provide four differentslices in processing a second request, when six slices were previouslyprovided in a first response from a different DSN access portal when thepillar width is 16, the reconstruction threshold is 10, the securitylevel is six, and the security parameters is five.

The method continues with step 318 where the processing module retrievesthe set of encoded data slices from dispersed storage units, wherein theset of encoded data slices includes less than a reconstruction thresholdnumber of encoded data slices. Next, at step 320 processing modulegenerates a response that includes the set of encoded data slices. Inaddition, the processing module sends the response to the requester.

As may be used herein, the terms “substantially” and “approximately”provides an industry-accepted tolerance for its corresponding termand/or relativity between items. Such an industry-accepted toleranceranges from less than one percent to fifty percent and corresponds to,but is not limited to, component values, integrated circuit processvariations, temperature variations, rise and fall times, and/or thermalnoise. Such relativity between items ranges from a difference of a fewpercent to magnitude differences. As may also be used herein, theterm(s) “coupled to” and/or “coupling” and/or includes direct couplingbetween items and/or indirect coupling between items via an interveningitem (e.g., an item includes, but is not limited to, a component, anelement, a circuit, and/or a module) where, for indirect coupling, theintervening item does not modify the information of a signal but mayadjust its current level, voltage level, and/or power level. As mayfurther be used herein, inferred coupling (i.e., where one element iscoupled to another element by inference) includes direct and indirectcoupling between two items in the same manner as “coupled to”. As mayeven further be used herein, the term “operable to” indicates that anitem includes one or more of power connections, input(s), output(s),etc., to perform one or more its corresponding functions and may furtherinclude inferred coupling to one or more other items. As may stillfurther be used herein, the term “associated with”, includes directand/or indirect coupling of separate items and/or one item beingembedded within another item. As may be used herein, the term “comparesfavorably”, indicates that a comparison between two or more items,signals, etc., provides a desired relationship. For example, when thedesired relationship is that signal 1 has a greater magnitude thansignal 2, a favorable comparison may be achieved when the magnitude ofsignal 1 is greater than that of signal 2 or when the magnitude ofsignal 2 is less than that of signal 1.

The present invention has also been described above with the aid ofmethod steps illustrating the performance of specified functions andrelationships thereof. The boundaries and sequence of these functionalbuilding blocks and method steps have been arbitrarily defined hereinfor convenience of description. Alternate boundaries and sequences canbe defined so long as the specified functions and relationships areappropriately performed. Any such alternate boundaries or sequences arethus within the scope and spirit of the claimed invention.

The present invention has been described above with the aid offunctional building blocks illustrating the performance of certainsignificant functions. The boundaries of these functional buildingblocks have been arbitrarily defined for convenience of description.Alternate boundaries could be defined as long as the certain significantfunctions are appropriately performed. Similarly, flow diagram blocksmay also have been arbitrarily defined herein to illustrate certainsignificant functionality. To the extent used, the flow diagram blockboundaries and sequence could have been defined otherwise and stillperform the certain significant functionality. Such alternatedefinitions of both functional building blocks and flow diagram blocksand sequences are thus within the scope and spirit of the claimedinvention. One of average skill in the art will also recognize that thefunctional building blocks, and other illustrative blocks, modules andcomponents herein, can be implemented as illustrated or by discretecomponents, application specific integrated circuits, processorsexecuting appropriate software and the like or any combination thereof.

What is claimed is:
 1. A method comprises: receiving, by a firstcomputing device, a first request from a user device to access securedata, wherein the first request includes a user identification code (ID)and at least one object name for the secure data; processing, by thefirst computing device, the first request to determine a level of accessto the secure data for the user device; when the level of access is ofan acceptable level, facilitating, by the first computing device,sending a set of encoded data slices to the user device, wherein the setof encoded data slices includes less than a reconstruction thresholdnumber of encoded data slices to reconstruct at least a segment of thesecure data; receiving, by a second computing device, a second requestfrom the user device to access the secure data, wherein the secondrequest includes the user ID, the at least one object name for thesecure data, and a representation of the first request; processing, bythe second computing device, the second request to determine the levelof access to the secure data for the user device; and when the level ofaccess is of the acceptable level, facilitating, by the second computingdevice, sending a second set of encoded data slices to the user device,wherein the second set of encoded data slices includes less than thereconstruction threshold number of encoded data slices and wherein, whenthe level of access is at a given level, the set of encoded data slicesand the second set of encoded data slices includes at least thereconstruction threshold number of encoded data slices.
 2. The method ofclaim 1, wherein the processing the first request comprises: determininga security level associated with the user device; and determiningsecurity parameters associated with the secure data, wherein the firstcomputing device determines the level of access to the secure data basedon the security level associated with the user device and the securityparameters.
 3. The method of claim 1, wherein the facilitating thesending of the set of encoded data slices to the user device comprises:when the acceptable level is a partial access level: retrieving the setof encoded data slices from dispersed storage units; generating aresponse that includes the set of encoded data slices; and sending theresponse to the user device.
 4. The method of claim 1, wherein theprocessing the first request further comprises: communicating with adispersed storage (DS) managing unit regarding a security levelassociated with the user device; and communicating with the dispersedstorage (DS) managing unit regarding security parameters associated withthe secure data, wherein the first computing device determines the levelof access to the secure data based on the security level associated withthe user device and the security parameters.
 5. The method of claim 1,wherein the processing the first request comprises: determining whetherthe first request includes a representation of a response from anothercomputing device; when the first request does not include therepresentation, determining whether the first request is an initialrequest for the secure data by the user device; and when the firstrequest is not the initial request, determining that the level of accessis not acceptable for facilitating sending of the set of encoded dataslices.
 6. The method of claim 1, wherein the processing the firstrequest comprises: determining a number of encoded data slices toinclude in the set of encoded data slices based on a variable functionof security parameters and a security level associated with the user ID,wherein the security parameters includes at least one of: a secrecylevel of data, an amount of data, codec information regarding the data,and error coding dispersal storage function parameters.
 7. The method ofclaim 1, wherein the processing the second request comprises:determining a security level associated with the user device;determining security parameters associated with the secure data;verifying the representation of the first request; and when therepresentation of the first request is verified, determining the levelof access to the secure data based on the security level associated withthe user device and the security parameters.
 8. The method of claim 1,wherein the facilitating the sending of the second set of encoded dataslices to the user device comprises: when the acceptable level is apartial access level: retrieving the second set of encoded data slicesfrom dispersed storage units; generating a response that includes thesecond set of encoded data slices; and sending the response to the userdevice.
 9. The method of claim 1, wherein the secure data includes oneor more of: financial account information; user password information;security credential information; and personal data.
 10. A computerreadable storage medium comprises: a first storage device that storesoperational instructions that, when executed by a first computingdevice, causes the first computing device to: receive a first requestfrom a user device to access secure data, wherein the first requestincludes a user identification code (ID) and at least one object namefor the secure data; process the first request to determine a level ofaccess to the secure data for the user device; when the level of accessis of an acceptable level, facilitate sending a set of encoded dataslices to the user device, wherein the set of encoded data slicesincludes less than a reconstruction threshold number of encoded dataslices to reconstruct at least a segment of the secure data; a secondstorage device that stores operational instructions that, when executedby a second computing device, causes the second computing device to:receive a second request from the user device to access the secure data,wherein the second request includes the user ID, the at least one objectname for the secure data, and a representation of the first request;process the second request to determine the level of access to thesecure data for the user device; and when the level of access is of theacceptable level, facilitate sending a second set of encoded data slicesto the user device, wherein the second set of encoded data slicesincludes less than the reconstruction threshold number of encoded dataslices and wherein, when the level of access is at a given level, theset of encoded data slices and the second set of encoded data slicesincludes at least the reconstruction threshold number of encoded dataslices.
 11. The computer readable storage medium of claim 10, whereinthe first storage device further stores operational instructions that,when executed by the first computing device, causes the first computingdevice to process the first request by: determining a security levelassociated with the user device; and determining security parametersassociated with the secure data, wherein the first computing devicedetermines the level of access to the secure data based on the securitylevel associated with the user device and the security parameters. 12.The computer readable storage medium of claim 10, wherein the firststorage device further stores operational instructions that, whenexecuted by the first computing device, causes the first computingdevice to facilitate the sending of the set of encoded data slices tothe user device by: when the acceptable level is a partial access level:retrieving the set of encoded data slices from dispersed storage units;generating a response that includes the set of encoded data slices; andsending the response to the user device.
 13. The computer readablestorage medium of claim 10, wherein the first storage device furtherstores operational instructions that, when executed by the firstcomputing device, causes the first computing device to process the firstrequest further by: communicating with a dispersed storage (DS) managingunit regarding a security level associated with the user device; andcommunicating with the dispersed storage (DS) managing unit regardingsecurity parameters associated with the secure data, wherein the firstcomputing device determines the level of access to the secure data basedon the security level associated with the user device and the securityparameters.
 14. The computer readable storage medium of claim 10,wherein the first storage device further stores operational instructionsthat, when executed by the first computing device, causes the firstcomputing device to process the first request by: determining whetherthe first request includes a representation of a response from anothercomputing device; when the first request does not include therepresentation, determining whether the first request is an initialrequest for the secure data by the user device; and when the firstrequest is not the initial request, determining that the level of accessis not acceptable for facilitating sending of the set of encoded dataslices.
 15. The computer readable storage medium of claim 10, whereinthe first storage device further stores operational instructions that,when executed by the first computing device, causes the first computingdevice to process the first request by: determining a number of encodeddata slices to include in the set of encoded data slices based on avariable function of security parameters and a security level associatedwith the user ID, wherein the security parameters includes at least oneof: a secrecy level of data, an amount of data, codec informationregarding the data, and error coding dispersal storage functionparameters.
 16. The computer readable storage medium of claim 10,wherein the second storage device further stores operationalinstructions that, when executed by the second computing device, causesthe second computing device to process the second request by:determining a security level associated with the user device;determining security parameters associated with the secure data;verifying the representation of the first request; and when therepresentation of the first request is verified, determining the levelof access to the secure data based on the security level associated withthe user device and the security parameters.
 17. The computer readablestorage medium of claim 10, wherein the second storage device furtherstores operational instructions that, when executed by the secondcomputing device, causes the second computing device to facilitate thesending of the second set of encoded data slices to the user device by:when the acceptable level is a partial access level: retrieving thesecond set of encoded data slices from dispersed storage units;generating a response that includes the second set of encoded dataslices; and sending the response to the user device.
 18. The computerreadable storage medium of claim 10, wherein the secure data includesone or more of: financial account information; user passwordinformation; security credential information; and personal data.